| 7 |
 | 8.5.4 |
| |
| 52 |
|  |
| 82 |
| 8.5.3 FP5 |
| |
| 86 |
| |
| 180 |
| 8.5.3 FP3 |
| |
| 127 |
| |
| 132 |
| 8.5.3 FP1 |
| |
| 1264 |
| |
| 149 |
| 8.5.2 FP4 |
| |
| 241 |
| |
| 142 |
| 8.5.2 FP2 |
| |
| 172 |
| |
| 1944 |
| 8.5.2 |
| |
| 131 |
| |
| 1 |
|
| Activity Logging |
| |
| 1 |
|
| |
| 3 |
|
| Attachments |
| |
| 1 |
|
| |
| 13 |
|
| Client UI |
| |
| 1 |
|
| |
| 1 |
|
| Commposite Applications |
| |
| 1 |
|
| |
| 1 |
|
| DAOS |
| |
| 2 |
|
| |
| 4 |
|
 | Database Transaction Logging/Recovery |
| |
| | | | FMEG8448Y6 | This fix address a log file full issue for which there is no indication of why (no long held lock or error messages). | |
| | | | SWAS86GP5D | Fixed a bad nlogctrl.lfh file that was created in Domino 8.5.1x with archive style transaction logging configured. This regression was introduced in... | |
| | | | RCOR7KWFJQ | Addresses log file full due to error from hlgSetLogLSNArray. | |
| | | | SWAS86GNJB | After recovering a database and applying the transaction logs (archive style logging), the retrieved log extents were left in the log directory. ... | |
| 2 |
|
| |